| Package | hl7.ehrs.uv.phrsfmr2 |
| Type | Requirements |
| Id | Id |
| FHIR Version | R5 |
| Source | http://hl7.org/ehrs/uv/phrsfmr2/https://build.fhir.org/ig/HL7/phrsfm-ig/Requirements-PHRSFMR2-PH.2.1.html |
| Url | http://hl7.org/ehrs/uv/phrsfmr2/Requirements/PHRSFMR2-PH.2.1 |
| Version | 2.0.1-ballot |
| Status | active |
| Date | 2025-04-03T15:15:30+00:00 |
| Name | PH_2_1_Manage_PHR_Account_Holder_Originated_Data |
| Title | PH.2.1 Manage PHR Account Holder Originated Data (Function) |
| Experimental | False |
| Authority | hl7 |
| Description | Manage information sourced or input directly by the PHR Account Holder. |
| Purpose | PHR data, including personal observations and most specific data elements (such as allergies and intolerances or problems), may be entered directly by the PHR Account Holder. The source of all data is captured and, in this case, self-entered data, should be so labeled. These data elements may possess more or less credibility when entered by the PHR Account Holder. When appropriate, patient-entered data should be structured and codified. Paper-based information (such as a health card or a laboratory report) may be captured in the form of a scanned image and kept in the record, organized, and/or indexed for retrieval. Example(s): When a problem in the problem list is entered by the PHR Account Holder, it is labeled as such in order to distinguish this problem from others that resulted from a provider’s clinical diagnosis. |
No resources found
No resources found
Note: links and images are rebased to the (stated) source
Manage information sourced or input directly by the PHR Account Holder.
PHR data, including personal observations and most specific data elements (such as allergies and intolerances or problems), may be entered directly by the PHR Account Holder. The source of all data is captured and, in this case, self-entered data, should be so labeled. These data elements may possess more or less credibility when entered by the PHR Account Holder. When appropriate, patient-entered data should be structured and codified.
Paper-based information (such as a health card or a laboratory report) may be captured in the form of a scanned image and kept in the record, organized, and/or indexed for retrieval.
Example(s): When a problem in the problem list is entered by the PHR Account Holder, it is labeled as such in order to distinguish this problem from others that resulted from a provider’s clinical diagnosis.
| PH.2.1#01 | SHALL |
The system SHALL conform to RI.1.1.1 (Originate and Retain Record Entry) in order to capture unstructured PHR Account Holder -originated data. |
| PH.2.1#02 | SHALL |
The system SHALL conform to RI.1.1.1 (Originate and Retain Record Entry) in order to capture structured PHR Account Holder -originated data. |
| PH.2.1#03 | SHALL |
The system SHALL conform to RI.1.1.1.1 (Evidence of Record Entry Originate / Retain Event) in order to manage metadata that identifies the author of the data (e.g., the PHR Account Holder as author or a provider as author), or the source of the data (e.g., the name and location of an external system that authored and transmitted the data), or the generator of the data (e.g., the Unique Device Identifier and metadata of a medical device that authored the data). |
| PH.2.1#04 | SHOULD |
The system SHOULD render PHR Account Holder -originated data for use by care providers. |
| PH.2.1#05 | MAY |
The system MAY provide the ability to capture an indication that a provider has verified the accuracy of consumer-originated data and has included it as a record in the EHR-S. |
| PH.2.1#06 | MAY |
The system MAY provide the ability for the PHR Account Holder to annotate PHR Account Holder -sourced data with text comments. |
| PH.2.1#07 | MAY |
The system MAY provide the ability for the PHR Account Holder to update PHR Account Holder-sourced data with text comments. |
FHIR{
"resourceType" : "Requirements",
"id" : "PHRSFMR2-PH.2.1",
"meta" : {
"profile" : [
"http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/FMFunction"
]
},
"text" : {
"status" : "extensions",
"div" : "<div xmlns=\"http://www.w3.org/1999/xhtml\">\n <span id=\"description\"><b>Statement <a href=\"https://hl7.org/fhir/versions.html#std-process\" title=\"Normative Content\" class=\"normative-flag\">N</a>:</b> <div><p>Manage information sourced or input directly by the PHR Account Holder.</p>\n</div></span>\n\n \n <span id=\"purpose\"><b>Description <a href=\"https://hl7.org/fhir/versions.html#std-process\" title=\"Informative Content\" class=\"informative-flag\">I</a>:</b> <div><p>PHR data, including personal observations and most specific data elements (such as allergies and intolerances or problems), may be entered directly by the PHR Account Holder. The source of all data is captured and, in this case, self-entered data, should be so labeled. These data elements may possess more or less credibility when entered by the PHR Account Holder. When appropriate, patient-entered data should be structured and codified.</p>\n<p>Paper-based information (such as a health card or a laboratory report) may be captured in the form of a scanned image and kept in the record, organized, and/or indexed for retrieval.</p>\n<p>Example(s): When a problem in the problem list is entered by the PHR Account Holder, it is labeled as such in order to distinguish this problem from others that resulted from a provider’s clinical diagnosis.</p>\n</div></span>\n \n\n \n <span id=\"actors\"><b>Actors:</b><br/> ehr</span>\n \n\n \n <span id=\"requirements\"><b>Criteria <a href=\"https://hl7.org/fhir/versions.html#std-process\" title=\"Normative Content\" class=\"normative-flag\">N</a>:</b></span>\n \n <table id=\"statements\" class=\"grid dict\">\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>PH.2.1#01</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHALL</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHALL conform to RI.1.1.1 (Originate and Retain Record Entry) in order to capture unstructured PHR Account Holder -originated data.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>PH.2.1#02</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHALL</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHALL conform to RI.1.1.1 (Originate and Retain Record Entry) in order to capture structured PHR Account Holder -originated data.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>PH.2.1#03</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHALL</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHALL conform to RI.1.1.1.1 (Evidence of Record Entry Originate / Retain Event) in order to manage metadata that identifies the author of the data (e.g., the PHR Account Holder as author or a provider as author), or the source of the data (e.g., the name and location of an external system that authored and transmitted the data), or the generator of the data (e.g., the Unique Device Identifier and metadata of a medical device that authored the data).</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>PH.2.1#04</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHOULD</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHOULD render PHR Account Holder -originated data for use by care providers.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>PH.2.1#05</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>MAY</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system MAY provide the ability to capture an indication that a provider has verified the accuracy of consumer-originated data and has included it as a record in the EHR-S.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>PH.2.1#06</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>MAY</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system MAY provide the ability for the PHR Account Holder to annotate PHR Account Holder -sourced data with text comments.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>PH.2.1#07</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>MAY</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system MAY provide the ability for the PHR Account Holder to update PHR Account Holder-sourced data with text comments.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n </table>\n</div>"
},
"extension" : [
{
"url" : "http://hl7.org/fhir/StructureDefinition/structuredefinition-wg",
"valueCode" : "ehr"
}
],
"url" : "http://hl7.org/ehrs/uv/phrsfmr2/Requirements/PHRSFMR2-PH.2.1",
"version" : "2.0.1-ballot",
"name" : "PH_2_1_Manage_PHR_Account_Holder_Originated_Data",
"title" : "PH.2.1 Manage PHR Account Holder Originated Data (Function)",
"status" : "active",
"date" : "2025-04-03T15:15:30+00:00",
"publisher" : "EHR WG",
"contact" : [
{
"telecom" : [
{
"system" : "url",
"value" : "http://www.hl7.org/Special/committees/ehr"
}
]
}
],
"description" : "Manage information sourced or input directly by the PHR Account Holder.",
"purpose" : "PHR data, including personal observations and most specific data elements (such as allergies and intolerances or problems), may be entered directly by the PHR Account Holder. The source of all data is captured and, in this case, self-entered data, should be so labeled. These data elements may possess more or less credibility when entered by the PHR Account Holder. When appropriate, patient-entered data should be structured and codified.\r\n\r\nPaper-based information (such as a health card or a laboratory report) may be captured in the form of a scanned image and kept in the record, organized, and/or indexed for retrieval.\r\n\r\nExample(s): When a problem in the problem list is entered by the PHR Account Holder, it is labeled as such in order to distinguish this problem from others that resulted from a provider’s clinical diagnosis.",
"statement" : [
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "PHRSFMR2-PH.2.1-01",
"label" : "PH.2.1#01",
"conformance" : [
"SHALL"
],
"conditionality" : false,
"requirement" : "The system SHALL conform to RI.1.1.1 (Originate and Retain Record Entry) in order to capture unstructured PHR Account Holder -originated data."
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "PHRSFMR2-PH.2.1-02",
"label" : "PH.2.1#02",
"conformance" : [
"SHALL"
],
"conditionality" : false,
"requirement" : "The system SHALL conform to RI.1.1.1 (Originate and Retain Record Entry) in order to capture structured PHR Account Holder -originated data."
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "PHRSFMR2-PH.2.1-03",
"label" : "PH.2.1#03",
"conformance" : [
"SHALL"
],
"conditionality" : false,
"requirement" : "The system SHALL conform to RI.1.1.1.1 (Evidence of Record Entry Originate / Retain Event) in order to manage metadata that identifies the author of the data (e.g., the PHR Account Holder as author or a provider as author), or the source of the data (e.g., the name and location of an external system that authored and transmitted the data), or the generator of the data (e.g., the Unique Device Identifier and metadata of a medical device that authored the data)."
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "PHRSFMR2-PH.2.1-04",
"label" : "PH.2.1#04",
"conformance" : [
"SHOULD"
],
"conditionality" : false,
"requirement" : "The system SHOULD render PHR Account Holder -originated data for use by care providers."
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "PHRSFMR2-PH.2.1-05",
"label" : "PH.2.1#05",
"conformance" : [
"MAY"
],
"conditionality" : false,
"requirement" : "The system MAY provide the ability to capture an indication that a provider has verified the accuracy of consumer-originated data and has included it as a record in the EHR-S."
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "PHRSFMR2-PH.2.1-06",
"label" : "PH.2.1#06",
"conformance" : [
"MAY"
],
"conditionality" : false,
"requirement" : "The system MAY provide the ability for the PHR Account Holder to annotate PHR Account Holder -sourced data with text comments."
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "PHRSFMR2-PH.2.1-07",
"label" : "PH.2.1#07",
"conformance" : [
"MAY"
],
"conditionality" : false,
"requirement" : "The system MAY provide the ability for the PHR Account Holder to update PHR Account Holder-sourced data with text comments."
}
]
}
XIG built as of ??metadata-date??. Found ??metadata-resources?? resources in ??metadata-packages?? packages.